-
Notifications
You must be signed in to change notification settings - Fork 70
[Tuner] Expand tuning candidate logging feature #2666
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2666 +/- ##
=======================================
Coverage ? 77.03%
=======================================
Files ? 291
Lines ? 28892
Branches ? 0
=======================================
Hits ? 22257
Misses ? 6635
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
kuhar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall, just a few minor comments
Co-authored-by: Jakub Kuderski <[email protected]>
This PR expands the logging function to support data analysis of the candidate search space and
candidate_orderingperformance evaluation.Tuner now records candidate info such as tuning knob configurations, position in benchmark queue, final result ranking, etc.
The collected tuning records will be exported to a CSV file under the tuning base folder.